home *** CD-ROM | disk | FTP | other *** search
- Path: doc.ic.ac.uk!not-for-mail
- From: mdf@doc.ic.ac.uk (Martin Frost)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Strange guru
- Date: 1 Mar 1996 13:03:28 -0000
- Organization: Dept. of Computing, Imperial College, University of London, UK.
- Distribution: world
- Message-ID: <4h6sj0$l59@oak43.doc.ic.ac.uk>
- References: <4gscv0$ovd@brachio.zrz.TU-Berlin.DE> <4h3ivo$966@hasle.sn.no>
- Reply-To: mdf@doc.ic.ac.uk (Martin Frost)
- NNTP-Posting-Host: oak43.doc.ic.ac.uk
- X-Newsreader: mxrn 6.18-23
-
-
- In article <4h3ivo$966@hasle.sn.no>, jakob.rivertz@aftenposten.no (Jakob Rivertz) writes:
-
- >Do a GetMsg() on process->pr_MsgPort when your program starts. If
- >it returns non-NULL, then hold onto this message until your code can
- >exit. Then reply the message. WB will then UnLoadSeg() your code.
-
- What is documented in the RKMs as required is to check proc->pr_CLI and if
- this is zero then do a WaitPort(proc->pr_MsgPort) and then the GetMsg().
- At present this works without the WaitPort(), but it could be needed in the
- future. Also, you need to reply the message in a Forbid(), and I put a
- Wait(0L) after the ReplyMsg(), just in case.
-
- Martin
-